| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-AS.7.2.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.7.2 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | AS_7_2_Support_Encounter_Documentation |
| Title | AS.7.2 Support Encounter Documentation (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Provide assistance in assembling data, supporting data collection and processing output from a specific encounter. |
| Purpose | Workflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Provide assistance in assembling data, supporting data collection and processing output from a specific encounter.
Workflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry.
| AS.7.2#01 | SHOULD |
The system SHOULD determine and render workflow support for data collection in a care setting. |
| AS.7.2#02 | SHOULD |
The system SHOULD provide the ability to capture and maintain encounter and care setting specific data entry workflows. |
| AS.7.2#03 | SHOULD |
The system SHOULD provide the ability to extract information from the patient record as necessary to support documentation of the patient encounter. |
| AS.7.2#04 | SHOULD |
The system SHOULD capture and maintain a reduced set of diagnostic and procedure codes for the care setting. |
| AS.7.2#05 | MAY |
The system MAY analyze the information entered into the encounter and, based on business rules, initiate secondary reporting workflows. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-AS.7.2",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Provide assistance in assembling data, supporting data collection and processing output from a specific encounter.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>Workflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.2#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD determine and render workflow support for data collection in a care setting.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.2#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain encounter and care setting specific data entry workflows.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.2#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to extract information from the patient record as necessary to support documentation of the patient encounter.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.2#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD capture and maintain a reduced set of diagnostic and procedure codes for the care setting.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>AS.7.2#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY analyze the information entered into the encounter and, based on business rules, initiate secondary reporting workflows.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-AS.7.2",
"version" : "2.1.0",
"name" : "AS_7_2_Support_Encounter_Documentation",
"title" : "AS.7.2 Support Encounter Documentation (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Provide assistance in assembling data, supporting data collection and processing output from a specific encounter.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "Workflows, based on the encounter management settings, will assist (with triggers alerts and other means) in determining and supportingdata collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.2-01",
"label" : "AS.7.2#01",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD determine and render workflow support for data collection in a care setting.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.2#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.2-02",
"label" : "AS.7.2#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain encounter and care setting specific data entry workflows.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.2#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.2-03",
"label" : "AS.7.2#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to extract information from the patient record as necessary to support documentation of the patient encounter.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.2#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.2-04",
"label" : "AS.7.2#04",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD capture and maintain a reduced set of diagnostic and procedure codes for the care setting.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.2#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-AS.7.2-05",
"label" : "AS.7.2#05",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY analyze the information entered into the encounter and, based on business rules, initiate secondary reporting workflows.",
"derivedFrom" : "EHR-S_FM_R1.1 S.3.1.2#5"
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.